Tap to autofill card data

ABSTRACT

Various embodiments are generally directed to autofilling card data from a contactless card to a form of a computing device. An application may determine that a payment field of a form has received focus. The application may then receive encrypted data from a communications interface of a contactless card associated with an account. The application may then receive, from a server, verification of the encrypted data. The application may then receive, from the server, an encrypted account number associated with the account, and decrypt the encrypted account number to yield the account number. An autofill service of an operating system (OS) executing on the processor circuit, may then autofill the account number to the payment field of the form.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/256,983, entitled “TAP TO AUTOFILL CARD DATA” filed on Jan. 24, 2019.The contents of the aforementioned application are incorporated hereinby reference in their entirety.

TECHNICAL FIELD

Embodiments herein generally relate to computing platforms, and morespecifically, to tapping a card to a computing device to initiate theautofill of payment data into a payment form on the computing device.

BACKGROUND

Account identifiers for payment cards are often long numeric and/orcharacter strings. As such, it is difficult for a user to manually enterthe account identifier correctly. Indeed, users often make mistakes andenter incorrect account numbers into computing interfaces (e.g., paymentinterfaces). Furthermore, processes have been developed that allowcameras to capture and identify account identifiers entered in a device,thereby posing security risks to account identifiers.

SUMMARY

Embodiments disclosed herein provide systems, methods, articles ofmanufacture, and computer-readable media for tapping to autofill carddata to a form on a computing device. According to one example, anapplication may determine that a payment field of a form has receivedfocus. The application may then receive encrypted data from acommunications interface of a contactless card associated with anaccount, the encrypted data generated based on a cryptographic algorithmand a diversified key, the diversified key stored in a memory of thecontactless card and generated based on a master key and a counter valuestored in the memory of the contactless card. The application may thenreceive, from a server, verification of the encrypted data, the serverto decrypt the encrypted data based on the cryptographic algorithm andthe diversified key stored in a memory of the server to verify theencrypted data, the diversified key stored in the memory of the servergenerated based on a master key and a counter value stored in the memoryof the server. The application may then receive, from the server, anencrypted account number associated with the account, and decrypt theencrypted account number to yield the account number. An autofillservice of an operating system (OS) executing on the processor circuit,may then autofill the account number to the payment field of the form.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1B illustrate embodiments of a system for tapping to autofillcard data.

FIGS. 2A-2B illustrate embodiments of tapping to autofill card data.

FIGS. 3A-3D illustrate embodiments of tapping to autofill card data.

FIGS. 4A-4B illustrate an example contactless card.

FIG. 5 illustrates an embodiment of a first logic flow.

FIG. 6 illustrates an embodiment of a second logic flow.

FIG. 7 illustrates an embodiment of a third logic flow.

FIG. 8 illustrates an embodiment of a computing architecture.

DETAILED DESCRIPTION

Embodiments disclosed herein provide secure techniques to autofill carddata (e.g., an account number, expiration date, customer billingaddress, shipping address, and/or card verification value (CVV)) of acontactless card to a form of a computing device using an autofillservice and/or an accessibility service. Generally, a user of a devicemay select a form field associated with payment (e.g., an account numberfield, expiration date field, CVV field, name, shipping address, and/orbilling address), which brings focus to the form field. Upon determiningthe form field has received focus, the device may output an indicationto tap the contactless card to the device. The user may then tap thecontactless card to the device. The device may then instruct thecontactless card to generate and transmit data to the application. Insome embodiments, the data generated by the contactless card includesthe account number, expiration date, billing address, and/or CVV value.In other embodiments, the data generated by the contactless card may beencrypted using key diversification. The application may transmit theencrypted data received from the contactless card to a server forverification. Upon verifying the data, the server may transmit card data(e.g., an account number, expiration date, name, addresses, and/or CVV)to the device. Whether received from the contactless card, from theserver, or locally, the card data may then be provided to an autofillservice of the operating system of the device. The autofill service maythen automatically populate the card data to the form field (e.g.,populate the account number into an account number form field, etc.).

Advantageously, doing so improves security of all devices and associateddata. For example, conventional approaches require the user to manuallyenter the card data into a form. However, doing so may allow other usersor devices to capture the card data as the user enters the card datainto the form. By eliminating the need for the user to manually entercard data into the form, the security of the card data is enhanced.Furthermore, the validation performed by the server provides anadditional safeguard to ensure that the correct card data is beingentered into the form. Additionally, the generation and filling ofvirtual card numbers into the form protects the security of the actualaccount number of the contactless card, as conventional solutionsrequire providing the actual account number of the contactless card intothe form.

With general reference to notations and nomenclature used herein, one ormore portions of the detailed description which follows may be presentedin terms of program procedures executed on a computer or network ofcomputers. These procedural descriptions and representations are used bythose skilled in the art to most effectively convey the substances oftheir work to others skilled in the art. A procedure is here, andgenerally, conceived to be a self-consistent sequence of operationsleading to a desired result. These operations are those requiringphysical manipulations of physical quantities. Usually, though notnecessarily, these quantities take the form of electrical, magnetic, oroptical signals capable of being stored, transferred, combined,compared, and otherwise manipulated. It proves convenient at times,principally for reasons of common usage, to refer to these signals asbits, values, elements, symbols, characters, terms, numbers, or thelike. It should be noted, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to those quantities.

Further, these manipulations are often referred to in terms, such asadding or comparing, which are commonly associated with mentaloperations performed by a human operator. However, no such capability ofa human operator is necessary, or desirable in most cases, in any of theoperations described herein that form part of one or more embodiments.Rather, these operations are machine operations. Useful machines forperforming operations of various embodiments include digital computersas selectively activated or configured by a computer program storedwithin that is written in accordance with the teachings herein, and/orinclude apparatus specially constructed for the required purpose or adigital computer. Various embodiments also relate to apparatus orsystems for performing these operations. These apparatuses may bespecially constructed for the required purpose. The required structurefor a variety of these machines will be apparent from the descriptiongiven.

Reference is now made to the drawings, wherein like reference numeralsare used to refer to like elements throughout. In the followingdescription, for the purpose of explanation, numerous specific detailsare set forth in order to provide a thorough understanding thereof. Itmay be evident, however, that the novel embodiments can be practicedwithout these specific details. In other instances, well knownstructures and devices are shown in block diagram form in order tofacilitate a description thereof. The intention is to cover allmodification, equivalents, and alternatives within the scope of theclaims.

FIG. 1A depicts a schematic of an exemplary system 100, consistent withdisclosed embodiments. As shown, the system 100 includes one or morecontactless cards 101, one or more mobile devices 110, and a server 120.The contactless cards 101 are representative of any type of paymentcard, such as a credit card, debit card, ATM card, gift card, and thelike. The contactless cards 101 may comprise one or more chips (notdepicted), such as a radio frequency identification (RFID) chip,configured to communicate with the mobile devices 110 via NFC, the EMVstandard, or other short-range protocols in wireless communication.Although NFC is used as an example communications protocol, thedisclosure is equally applicable to other types of wirelesscommunications, such as the EMV standard, Bluetooth, and/or Wi-Fi. Themobile devices 110 are representative of any type of network-enabledcomputing devices, such as smartphones, tablet computers, wearabledevices, laptops, portable gaming devices, and the like. The server 120is representative of any type of computing device, such as a server,workstation, compute cluster, cloud computing platform, virtualizedcomputing system, and the like.

As shown, a memory 102 of the contactless card includes card data 103, acounter 104, a master key 105, a diversified key 106, a unique customeridentifier 107, and a data store of account numbers 108. The card data103 generally includes account-related information, such as informationused to process a payment using the contactless card 101. For example,the card data 103 may comprise an account number, an expiration date, abilling address, and a card verification value (CVV). The account numbermay be any type of account number, such as a primary account number(PAN), a virtual account number, and/or a token generated based on thePAN. Other types of account numbers are contemplated, and the use of theaccount number or other types of card data 103 should not be consideredlimiting of the disclosure. The card data 103 may further include names,billing address, shipping address, and other account-relatedinformation. The account numbers 108 store one-time-use virtual accountnumbers with associated expiration dates and CVV values. For example,the account numbers 108 may include thousands single-use virtual accountnumbers, expiration dates, and CVV values. As described in greaterdetail herein, the contactless card 101 may provide the card data 103and/or a record from the account numbers 108 to the account application113 to autofill to a form via the autofill service 114 and/or theaccessibility service 117.

As shown, a memory 111 of the mobile device 110 includes an instance ofan operating system (OS) 112. Example operating systems 112 include theAndroid® OS, iOS®, Linux®, and Windows® operating systems. As shown, theOS 112 includes an account application 113, an autofill service 114, oneor more other applications 115, a clipboard 116, and an accessibilityservice 117. The account application 113 allows users to perform variousaccount-related operations, such as viewing account balances, purchasingitems, and processing payments. Initially, a user must authenticateusing authentication credentials to access the account application 113.For example, the authentication credentials may include a username andpassword, biometric credentials, and the like.

The autofill service 114 is generally configured to fill out one or moreform fields by programmatically injecting data into the form fields.Stated differently, the autofill service 114 receives and stores datathat can be automatically injected into forms within the OS 112 and/orany applications (e.g., the account application 113 and/or otherapplications 115) executing in the OS 112. For example, as described ingreater detail herein, the autofill service 114 may automatically fillthe name, billing address, shipping address, account number, expirationdate, account billing address, and CVV fields of a form responsive to atap of the contactless card 101 to the mobile device 110. In someembodiments, the account number is a virtual account number. In someembodiments, the autofill service 114 is associated with the accountapplication 113. For example, the autofill service 114 may be installedon the mobile device 110 with the account application 113, and the useris prompted to enable the autofill service 114 subsequent to theinstallation. More generally, each time the account application 113 isopened, the account application 113 may determine whether the autofillservice 114 is enabled as the default autofill service for the OS 112.If the autofill service 114 is not enabled as the default autofillservice, the account application 113 may prompt the user to enable theautofill service 114 as the default autofill service for the OS 112.Once enabled as the default autofill service for the OS 112, theautofill service 114 may programmatically identify payment-relatedfields of forms, and prompt the user to tap a contactless card 101 tothe mobile device 110 to autofill form fields with data associated withthe contactless card 101 (e.g., one or more of a name, account number,expiration date, CVV, shipping address, and/or account billing address).

The accessibility service 117 is generally configured to assist users inusing the mobile device 110. For example, the accessibility service 117may automatically fill the name, account number, expiration date,shipping address, billing address, and CVV fields of a form responsiveto verification of the encrypted customer ID 109 by the server 120,where the encrypted customer ID 109 is generated by the contactless card101 responsive to a tap of the contactless card 101 to the mobile device110. In one embodiment, the accessibility service 117 is used toautofill the name, account number, expiration date, shipping address,billing address, and CVV data in a form in an application such as a webbrowser. The autofill service 114 is used as a reference example hereinfor programmatically filling card data into a form. However, use of theautofill service 114 should not be considered limiting of thedisclosure, as the disclosure is equally applicable to using theaccessibility service 117 or other services (e.g., a password service,or other types of services) to programmatically fill card data into aform.

As shown, the server 120 includes a data store of account data 124 and amemory 122. The account data 124 includes account-related data for aplurality of users and/or accounts. The account data 124 may include atleast a master key 105, counter 104, a customer ID 107, an associatedcontactless card 101, account holder name, account billing address, oneor more shipping addresses, one or more virtual card numbers, andbiographical information for each account. The memory 122 includes amanagement application 123 and instances of the card data 103, thecounter 104, master key 105, and diversified key 106 for one or moreaccounts from the account data 124.

The system 100 is configured to implement key diversification to securedata, which may be referred to as a key diversification techniqueherein. Generally, the server 120 (or another computing device) and thecontactless card 101 may be provisioned with the same master key 105(also referred to as a master symmetric key). More specifically, eachcontactless card 101 is programmed with a distinct master key 105 thathas a corresponding pair in the server 120. For example, when acontactless card 101 is manufactured, a unique master key 105 may beprogrammed into the memory 102 of the contactless card 101. Similarly,the unique master key 105 may be stored in a record of a customerassociated with the contactless card 101 in the account data 124 of theserver 120 (and/or stored in a different secure location). The masterkey may be kept secret from all parties other than the contactless card101 and server 120, thereby enhancing security of the system 100.

The master keys 105 may be used in conjunction with the counters 104 toenhance security using key diversification. The counters 104 comprisevalues that are synchronized between the contactless card 101 and server120. The counter value 104 may comprise a number that changes each timedata is exchanged between the contactless card 101 and the server 120(and/or the contactless card 101 and the mobile device 110). To enableNFC data transfer between the contactless card 101 and the mobile device110, the account application 113 may communicate with the contactlesscard 101 when the contactless card 101 is sufficiently close to a cardreader 118 of the mobile device 110. Card reader 118 may be configuredto read from and/or communicate with contactless card 101 (e.g., viaNFC, Bluetooth, RFID, etc.). Therefore, example card readers 118 includeNFC communication modules, Bluetooth communication modules, and/or RFIDcommunication modules.

For example, a user may tap the contactless card 101 to the mobiledevice 110, thereby bringing the contactless card 101 sufficiently closeto the card reader 118 of the mobile device 110 to enable NFC datatransfer between the contactless card 101 and the card reader 118 of themobile device 110. In some embodiments, the mobile device 110 maytrigger the card reader 118 via an API call. In addition and/oralternatively, the mobile device 110 may trigger the card reader 118based on periodically polling the card reader 118. More generally, themobile device 110 may trigger the card reader 118 to engage incommunications using any feasible method. After communication has beenestablished between mobile device 110 and contactless card 101, thecontactless card 101 generates a message authentication code (MAC)cryptogram. In some examples, this may occur when the contactless card101 is read by the account application 113. In particular, this mayoccur upon a read, such as an NFC read, of a near field data exchange(NDEF) tag, which may be created in accordance with the NFC DataExchange Format. For example, a reader, such as the account application113 and/or the card reader 118, may transmit a message, such as anapplet select message, with the applet ID of an NDEF producing applet.Upon confirmation of the selection, a sequence of select file messagesfollowed by read file messages may be transmitted. For example, thesequence may include “Select Capabilities file”, “Read Capabilitiesfile”, and “Select NDEF file”. At this point, the counter value 104maintained by the contactless card 101 may be updated or incremented,which may be followed by “Read NDEF file.” At this point, the messagemay be generated which may include a header and a shared secret. Sessionkeys may then be generated. The MAC cryptogram may be created from themessage, which may include the header and the shared secret. The MACcryptogram may then be concatenated with one or more blocks of randomdata, and the MAC cryptogram and a random number (RND) may be encryptedwith the session key. Thereafter, the cryptogram and the header may beconcatenated, and encoded as ASCII hex and returned in NDEF messageformat (responsive to the “Read NDEF file” message). In some examples,the MAC cryptogram may be transmitted as an NDEF tag, and in otherexamples the MAC cryptogram may be included with a uniform resourceindicator (e.g., as a formatted string). The contactless card 101 maythen transmit the MAC cryptogram to the mobile device 110, which maythen forward the MAC cryptogram to the server 120 for verification asexplained below. However, in some embodiments, the mobile device 110 mayverify the MAC cryptogram.

More generally, when preparing to send data (e.g., to the server 120and/or the mobile device 110), the contactless card 101 may incrementthe counter value 104. The contactless card 101 may then provide themaster key 105 and counter value 104 as input to a cryptographicalgorithm, which produces a diversified key 106 as output. Thecryptographic algorithm may include encryption algorithms, hash-basedmessage authentication code (HMAC) algorithms, cipher-based messageauthentication code (CMAC) algorithms, and the like. Non-limitingexamples of the cryptographic algorithm may include a symmetricencryption algorithm such as 3DES or AES128; a symmetric HMAC algorithm,such as HMAC-SHA-256; and a symmetric CMAC algorithm such as AES-CMAC.The contactless card 101 may then encrypt the data (e.g., the customeridentifier 107 and any other data) using the diversified key 106. Thecontactless card 101 may then transmit the encrypted data (e.g., theencrypted customer ID 109) to the account application 113 of the mobiledevice 110 (e.g., via an NFC connection, Bluetooth connection, etc.).The account application 113 of the mobile device 110 may then transmitthe encrypted data to the server 120 via the network 130. In at leastone embodiment, the contactless card 101 transmits the counter value 104with the encrypted data. In such embodiments, the contactless card 101may transmit an encrypted counter value 104, or an unencrypted countervalue 104.

Upon receiving the encrypted customer ID 109, the management application123 of the server 120 may perform the same symmetric encryption usingthe counter value 104 as input to the encryption, and the master key 105as the key for the encryption. As stated, the counter value 104 may bespecified in the data received from the mobile device 110, or a countervalue 104 maintained by the server 120 to implement key diversificationfor the contactless card 101. The output of the encryption may be thesame diversified key value 106 that was created by the contactless card101. The management application 123 may then decrypt the encryptedcustomer ID 109 received via the network 130 using the diversified key106, which reveals the data transmitted by the contactless card 101(e.g., at least the customer identifier 107). Doing so allows themanagement application 123 to verify the data transmitted by thecontactless card 101 via the mobile device 110, e.g., by comparing thedecrypted customer ID 107 to a customer ID in the account data 124 forthe account.

Although the counter 104 is used as an example, other data may be usedto secure communications between the contactless card 101, the mobiledevice 110, and/or the server 120. For example, the counter 104 may bereplaced with a random nonce, generated each time a new diversified key106 is needed, the full value of a counter value sent from thecontactless card 101 and the server 120, a portion of a counter valuesent from the contactless card 101 and the server 120, a counterindependently maintained by the contactless card 101 and the server 120but not sent between the two, a one-time-passcode exchanged between thecontactless card 101 and the server 120, and a cryptographic hash ofdata. In some examples, one or more portions of the diversified key 106may be used by the parties to create multiple diversified keys 106.

As shown, the server 120 may include one or more hardware securitymodules (HSM) 125. For example, one or more HSMs 125 may be configuredto perform one or more cryptographic operations as disclosed herein. Insome examples, one or more HSMs 125 may be configured as special purposesecurity devices that are configured to perform the one or morecryptographic operations. The HSMs 125 may be configured such that keysare never revealed outside the HSM 125, and instead are maintainedwithin the HSM 125. For example, one or more HSMs 125 may be configuredto perform at least one of key derivations, decryption, and MACoperations. The one or more HSMs 125 may be contained within, or may bein data communication with, server 120.

As stated, the key diversification technique may be used to performsecure operations using the contactless card 101. For example, once themanagement application 123 verifies the encrypted customer ID 109 usingkey diversification, the management application 123 may transmit anaccount number, expiration date, and/or CVV associated with the accountto the account application 113 of the mobile device 110. The managementapplication 123 may further include other information (e.g., first name,last name, shipping address, billing address, other account information,etc.). The account number may be a PAN, a virtual account number, and/ora token generated based on the PAN. The account application 113 maydecrypt the received data (if encrypted) and provide the account number,expiration date, billing address, and/or CVV to an applicationprogramming interface (API) of the autofill service 114. The autofillservice 114 may then automatically insert the account number in anaccount number field of a form, insert the expiration date in anexpiration date field (or fields) of a form, insert the CVV into a CVVfield of the form, insert the billing address into a billing addressfield of the form, insert the shipping address into a shipping addressfield of the form, and the name to a name field of the form.

In another embodiment, the card data 103 is read directly from thecontactless card 101, which may be useful if the mobile device 110 doesnot have a connection to the server 120. For example, the accountapplication 113 and/or the autofill service 114 may determine that auser has selected an account number field of a form, and that theaccount number field has received focus. In some embodiments, theaccount application 113 and/or autofill service 114 reads metadata of aform field to determine the type of information. For example, themetadata of a form field may specify that the form field is associatedwith the account number field, expiration date field, CVV field,shipping address field, and/or billing address field. In someembodiments, information such as the 16-digit card number, CVV, andcustomer name may be available offline, while other information such asaddresses and generated virtual numbers are not available offline andmay require a network connection. In response, the account application113 and/or the autofill service 114 may output an indication to tap thecontactless card 101 to the mobile device 110. In one embodiment, oncethe contactless card 101 is tapped to the mobile device 110, thecontactless card 101 transmits the card data 103 to the mobile device110. In another embodiment, once the contactless card 101 is tapped tothe mobile device 110, the account application 113 may instruct thecontactless card 101 to transmit the card data 103 to the mobile device110. In one example, the contactless card 101 transmits the card data103 (including one or more of the account number, expiration date, CVVvalue, the account holder's first name, and the account holder's lastname) to the mobile device 110 in an NDEF file (e.g. via NFC, Bluetooth,and/or RFID). In another example, the contactless card 101 transmits thecard data 103 using the EMV protocol. In examples where the EMV protocolis used, the card data 103 transmitted using the EMV protocol includesthe account number, expiration date, the account holder's first name,and the account holder's last name. The contactless card 101 may thentransmit the card data 103 to the account application 113 using the EMVprotocol. In examples where the EMV protocol is used, the accountapplication 113 may receive the CVV value from the contactless card 101(e.g., via the NFC read to receive the CVV in an NDEF file) and/or fromthe management application 123 of the server 120. However, in someembodiments, the EMV protocol may be used to transmit the CVV valuedirectly from the contactless card 101. The account application 113 maythen provide the card data 103 (e.g., the account number, expirationdate, and/or CVV) to the API of the autofill service 114. The autofillservice 114 may then autofill the card data 103 to the form. Forexample, the autofill service 114 may autofill the account number in theaccount number field of the form. Similarly, the autofill service 114may autofill the expiration date and/or CVV to the form.

In yet another embodiment, the contactless card 101 provides one of theaccount numbers 108 directly to the account application 113. Forexample, the account application 113 and/or the autofill service 114 maydetermine that a user has selected an account number field of a form,and that the account number field has received focus. For example, theaccount application 113 and/or the autofill service 114 may analyze anHTML attribute of the account number field to determine that the accountnumber field has received focus. Furthermore, the account application113 and/or the autofill service 114 may analyze the metadata of theaccount number field to determine that the field is associated with theaccount number. For example, the account application 113 and/or theautofill service 114 may determine, based on the metadata, that theaccount number field is configured to receive 16 characters as input. Asanother example, the metadata may specify a name for the form field thatis similar to names associated with account number fields (e.g.,“accountnumber”, “account_number”, etc.).

In response, the account application 113 and/or the autofill service 114may output an indication to tap the contactless card 101 to the mobiledevice 110. Once the contactless card 101 is tapped to the mobile device110, the account application 113 may instruct the contactless card 101to transmit one of the account numbers 108 to the account application113. The contactless card 101 may then select and encrypt an accountnumber 108 (which includes a virtual account number, expiration date,CVV, and optionally the account holder's first name and last name). Thecontactless card 101 may then mark the selected account number 108 asbeing used (e.g., by deleting the selected account number 108, updatinga “used” field or bit of the selected account number 108, etc.) andtransmit the encrypted account number 108 to the account application113. The account application 113 may then decrypt the account number 108and provide the decrypted data to the autofill service 114. The autofillservice 114 may then autofill one or more form fields with one or moreof the virtual account number, expiration date, and CVV (and optionallythe account holder's first name, last name, and billing address). Insome embodiments, to autofill one or more account numbers 108, thecontactless card 101 further generates an encrypted customer ID 109according to the key diversification technique. In such embodiments, theaccount application 113 may receive the encrypted customer ID 109 fromthe contactless card and transmit the encrypted customer ID 109 to themanagement application 123 of the server 120 for verification. Theaccount application 113 may wait for verification of the encryptedcustomer ID 109 before providing the account number, expiration date,and/or CVV to the autofill service 114. Therefore, if the encryptedcustomer ID 109 is not verified by the server 120, the accountapplication 113 does not provide the account number 108 to the autofillservice 114. However, in other embodiments, the verification of theencrypted customer ID 109 is not a condition to autofilling the virtualaccount numbers 108 of the contactless card 101.

Regardless of the technique used to provide card data 103 and/or theaccount number 108 to the autofill service 114, the account application113 and/or the OS 112 may manage the data provided to the autofillservice 114. For example, the card data 103 and/or the account number108 may be deleted from the autofill service 114 after being stored inthe autofill service 114 for a predefined amount of time. As anotherexample, the card data 103 and/or the account number 108 may be deletedfrom the autofill service 114 after the card data 103 and/or the accountnumber 108 has been used to make a purchase. Additionally and/oralternatively, the autofill service 114 may be modified to remove thecard data 103 and/or the account number 108, e.g., by copying randomdata to the autofill service 114.

Furthermore, the account application 113 and/or the autofill service 114may copy an account number to the clipboard 116 of the OS. The clipboard116 stores data that can be copied and/or pasted within the OS 112. Forexample, the clipboard 116 may store data locally for pasting intofields of the mobile device 110, and a user may input/paste the datastored in the clipboard 116 using a command and/or gesture availablewithin the OS 112. For example, copying the account number to theclipboard 116 allows the user to paste the account number to thecorresponding form field using a command and/or gesture available withinthe OS 112. Further still, the autofill service 114 may output anotification which specifies the expiration date and the CVV while theaccount number is copied to the clipboard 116. Doing so allows the userto manually enter the expiration date and CVV to the corresponding formfields while the notification remains in view. In some embodiments, theaccount application 113 and/or the autofill service 114 may also copythe expiration date, billing address, and/or the CVV to the clipboard116, allowing the expiration date, billing address, and/or the CVV to bepasted to the corresponding form fields.

FIG. 1B depicts an example of using the key diversification technique toautofill the card data 103 to a form. As shown, the account application113 includes a form 150. In operation, a user of the mobile device 110may select a field of the form 150 that is associated with payment(e.g., a name field, an account number field, an expiration date field,a CVV field, shipping address field, and/or a billing address field).The account application 113 and/or the autofill service 114 maydetermine that a payment field of the form 150 (and/or a form 151 of theother applications 115) has received focus, e.g., based on a name of thefield, a type of the field, etc. Generally, when a field of a formreceives focus, input may be provided to that field (whether manuallyvia user input, or programmatically via the autofill service 114 and/orthe accessibility service 117). The account application 113 and/or theautofill service 114 may then instruct the user to tap the contactlesscard 101 to the mobile device 110. Once the contactless card 101 istapped (e.g., brought within NFC communications range of the card reader118) to the mobile device 110, the account application 113 generates andtransmits an indication to the contactless card 101 to generate anencrypted customer ID 109 as depicted in FIG. 1A.

In response, the contactless card 101 increments the counter value 104and provides the master key 105 and counter value 104 as input to acryptographic algorithm, which produces a diversified key 106 as output.The contactless card 101 may then encrypt the customer identifier 107using the diversified key 106 to generate the encrypted customer ID 109.The contactless card 101 may then transmit the encrypted customer ID 109to the account application 113 of the mobile device 110 (e.g., via anNFC connection, Bluetooth connection, etc.). The account application 113of the mobile device 110 may then transmit the encrypted customer ID 109to the server 120 via the network 130. In at least one embodiment, thecontactless card 101 transmits the counter value 104 along with theencrypted customer ID 109.

Upon receipt of the encrypted customer ID 109 via the card reader 118,the management application 123 of the server 120 verifies the encryptedcustomer ID 109 using key diversification. As stated, the managementapplication 123 of the server 120 may perform the same symmetricencryption using the counter value 104 as input to the encryption, andthe master key 105 as the key for the encryption, to generate thediversified key 106. The management application 123 may then decrypt theencrypted customer ID 109 received via the network 130 using thediversified key 106, which reveals the data transmitted by thecontactless card 101 (e.g., at least the customer identifier 107). Doingso allows the management application 123 to verify the data transmittedby the contactless card 101 via the mobile device 110, e.g., bycomparing the decrypted customer ID 107 to a customer ID in the accountdata 124 for the account, where a match of the customer ID valuesverifies the encrypted data received from the contactless card 101. Insome embodiments, once the management application 123 verifies theencrypted customer ID 109, the management application 123 generates avirtual card number for the associated account, or causes a virtual cardnumber for the associated account to be generated.

As shown in FIG. 1B, after verifying the encrypted customer ID 109 ofFIG. 1A, the management application 123 of the server 120 transmits thecard data 103 from the server 120 to the mobile device 110. In at leastone embodiment, the management application 123 encrypts the card data103 before sending to the account application 113. As stated, the carddata 103 may include the account number, CVV, and/or expiration date ofthe contactless card 101. The card data 103 may further include theaccount holder's first name, last name, shipping address, and billingaddress. In one embodiment, the account number of the card data 103 isthe virtual card number generated subsequent to the verification of theencrypted customer ID 109 by the management application 123. In anotherembodiment, the account number of the card data 103 is a record from theaccount numbers 108. In one embodiment, the first and last names arestored in the account application 113 (or another element of the OS). Insuch embodiments, the account application 113 may provide the locallystored names to the autofill service 114 with the card data 103.Furthermore, as stated, the account number may comprise a virtualaccount number. The account application 113 may then receive the carddata 103 and decrypt the received card data 103 (if the card data 103has been encrypted). The account application 113 may then provide thecard data 103 to an API of the autofill service 114 (and/or theaccessibility service 117). The autofill service 114 and/or theaccessibility service 117 may then populate one or more fields of theform 150 (and/or the form 151 of the other applications 115) with thecorresponding card data 103 without requiring user input and withoutexposing the card data 103.

In one embodiment, the card data 103 sent by the server 120 to themobile device 110 includes all relevant information (e.g., the accountnumber, expiration date, CVV, billing address, shipping address, firstname, last name, etc.) required to make a purchase using the accountassociated with the contactless card 101. However, in other embodiments,the individual elements of the card data 103 may be incrementallyauto-filled by the autofill service 114 using one or more taps of thecontactless card 101 and the mobile device 110. For example, a first tapof the contactless card 101 and the mobile device 110 may cause theautofill service 114 to autofill the account number of the card data 103to an account number field of a form, while a second tap of thecontactless card 101 and the mobile device 110 may cause the autofillservice 114 to autofill the expiration date to an expiration date field(or fields) of the form, a third tap of the contactless card 101 and themobile device 110 may cause the autofill service 114 to autofill the CVVto a CVV field of the form, and a fourth tap of the contactless card 101and the mobile device 110 may cause the autofill service 114 to autofillthe billing address to a billing address field of the form. In oneembodiment, a separate encrypted customer ID 109 is generated by thecontactless card 101 responsive to each tap, and the server 120 verifieseach encrypted customer ID 109 before sending the corresponding carddata 103 to the mobile device 110. In another embodiment, a singleinstance of the encrypted customer ID 109 is generated responsive to theinitial tap, and the server 120 verifies this encrypted customer ID 109.In such an embodiment, the account application 113 may receive the name,account number, expiration date, CVV, shipping address, and billingaddress in a single response from the server 120, and provide the datato the autofill service 114 responsive to each tap of the contactlesscard 101 and the mobile device 110 based on a determination as to thedata needed for the form field currently in focus.

FIG. 2A is a schematic 200 depicting an example embodiment of tapping toautofill card data. A graphical user interface (GUI) of the accountapplication 113 on the mobile device 110 may include form fields201-205, where field 201 corresponds to an account number field, field202 corresponds to an expiration month field, field 203 corresponds toan expiration year field, field 204 corresponds to a CVV field, andfield 205 corresponds to a billing address field. As shown, anotification 206 is outputted by the autofill service 114 and/or theaccount application 113 when the account number field 201 receives focus(e.g., is selected by the user). The notification 206 instructs the userto tap the contactless card 101 to the mobile device 110. In oneembodiment, the user selects the notification 206 prior to tapping thecontactless card 101 to the mobile device 110.

Once the contactless card 101 is tapped to the mobile device 110, theaccount application 113 transmits, via the card reader 118 (e.g., viaNFC, Bluetooth, RFID, and/or the EMV protocol etc.), an indication tothe contactless card 101. In one embodiment, the indication may specifyto perform encryption using key diversification as depicted in FIG. 1A,in which case the account application 113 receives card data 103 fromthe server 120. In another embodiment, the indication may specify totransmit the card data 103 to the account application 113 in an NDEFfile (e.g., via NFC, Bluetooth, RFID, etc.), in which case the accountapplication 113 receives the card data 103 in an NDEF file directly fromthe contactless card 101 via the card reader 118. In another embodiment,the indication may specify to transmit the card data 103 to the accountapplication 113 via the EMV protocol, in which case the accountapplication 113 receives the card data 103 directly from the contactlesscard 101 via the EMV protocol. However, as stated, in embodiments wherethe EMV protocol is used, the CVV value is received from the contactlesscard 101 in an NDEF file and/or from the management application 123. Inanother embodiment, the indication may specify to perform encryptionusing key diversification as depicted in FIG. 1A and transmit an accountnumber 108 to the account application 113, in which case the accountapplication 113 receives a record from the account numbers 108 from thecontactless card 101 (which is used subject to verification of theencrypted customer ID 109 by the server 120). Regardless of theparticular technique used, the contactless card 101 and/or the server120 may transmit an account number, expiration date, CVV, accountbilling address, and/or an account holder's name to the accountapplication 113. However, as stated, in some embodiments, the accountholder's name is stored locally (e.g., in the account application 113),and is not received from the contactless card 101 and/or the server 120.As stated, the account number may be a PAN, virtual account number,and/or a token generated based on the PAN. If the received data isencrypted, the account application 113 may decrypt the data. The accountapplication 113 may then provide the decrypted account number,expiration date, and/or CVV to an API of the autofill service 114, whichautofills the form fields 201-204 with the received data.

FIG. 2B is a schematic 210 depicting the account application 113 afterthe autofill service 114 has auto-filled the account number into theaccount number field 201, the expiration month into the expiration monthfield 202, the expiration year into the expiration year field 203, theCVV into the CVV field 204, and the billing address into the billingaddress field 205. The particular values depicted in FIG. 2B areexemplary and should not be considered limiting of the disclosure.Furthermore, as stated, the autofill service 114 may further autofillthe account holder's name into a name field 207 of the form.

FIG. 3A is a schematic 300 depicting an example embodiment of tapping toautofill card data. Generally, FIGS. 3A-3D reflect an embodiment wheresuccessive taps are used to autofill an account number, expiration date,and CVV to a form. As shown, the GUI of the account application 113includes a form having fields 301-303, where field 301 is an accountnumber field, field 302 is an expiration date field, and field 303 is aCVV field. As shown, the account application 113 and/or the autofillservice 114 on the mobile device 110 may output a notification 304specifying to tap the contactless card 101 to the mobile device 110,e.g., responsive to determining the field 301 has received focus.

Once the contactless card 101 is tapped to the mobile device 110, theaccount application 113 transmits, via the card reader 118, anindication to the contactless card 101 to transmit data. For example,the indication may specify to transmit the account number of the carddata 103 directly to the mobile device 110 via the EMV protocol. Inresponse, the contactless card 101 may transmit the account number ofthe card data 103 via the EMV protocol. In another embodiment, theindication may specify to transmit a virtual account number from theaccount numbers 108. In response, the contactless card 101 may transmitthe virtual account number from the account numbers 108 to the accountapplication 113 via NFC. However, as stated, in embodiments where thevirtual account numbers 108 are used, the contactless card 101 maygenerate an encrypted customer ID 109 using key diversification, whichis provided to the account application 113 and transmitted to the server120 for verification.

In another embodiment, the indication may specify to the contactlesscard 101 to perform encryption using key diversification as describedabove to generate encrypted data (e.g., the encrypted customer ID 109),and transmit the encrypted data to the account application 113. Theaccount application 113 may then transmit the encrypted data to theserver 120, where the management application 123 verifies the encrypteddata using key diversification as described above. The managementapplication 123 may then transmit the account number to the accountapplication 113.

Regardless of the technique used to receive the account number, theaccount application 113 may provide the received account number to theAPI of the autofill service 114. As depicted in schematic 310 of FIG.3B, the autofill service 114 may then autofill the account number to theaccount number field 301. Furthermore, once the user taps the expirationdate field 302, the account application 113 and/or the autofill service114 may output a notification 305 to tap the contactless card 101 toautofill the expiration date to the expiration date field 302.

Responsive to the tap of the contactless card 101 to the mobile device110, the account application 113 receives the expiration date of thecontactless card 101. As stated, in one embodiment, the accountapplication 113 may receive the expiration date directly from thecontactless card 101 using the EMV protocol. In another embodiment, thecontactless card 101 may transmit the expiration date from the accountnumbers 108 (e.g., the expiration date of the virtual account numberfrom the account numbers 108 auto-filled in account number field 301).In another embodiment, the account application 113 receives theexpiration date from the management application 123 of the server basedon verification of encrypted data generated by the contactless card 101.Once received, the account application 113 provides the expiration dateto the API of the autofill service 114.

FIG. 3C is a schematic 320 illustrating an embodiment where the autofillservice 114 has auto-filled the expiration date to the expiration datefield 302. Furthermore, once the user taps the CVV field 303, theaccount application 113 may output a notification 307 to tap thecontactless card 101 to autofill the CVV of the contactless card 101 tothe CVV field 303. Responsive to the tap of the contactless card 101 tothe mobile device 110, the account application 113 receives the CVVvalue of the contactless card 101. As stated, in one embodiment, theaccount application 113 may receive the CVV value directly from thecontactless card 101 in an NDEF file (e.g., via NFC, RFID, Bluetooth,etc.). In another embodiment, the contactless card 101 may transmit theCVV from the account numbers 108 (e.g., the CVV value of the virtualaccount number from the account numbers 108 auto-filled in accountnumber field 301). In another embodiment, the account application 113receives the CVV value from the management application 123 of the serverbased on verification of encrypted data generated by the contactlesscard 101. Once received, the account application 113 provides the CVVvalue to the API of the autofill service 114.

FIG. 3D is a schematic 330 illustrating an embodiment where the autofillservice 114 has auto-filled the CVV value to the CVV field 303. Althoughnot depicted, in some embodiments, the billing address may beauto-filled into a billing address field of the form responsive to a tapof the contactless card 101 to the mobile device. Doing so allows forautomatic entry of the data required to complete a purchase ortransaction, which the user may complete via the GUI element 308.

In some embodiments, the initial tap of the contactless card 101 to themobile device 110 (e.g., the tap depicted in FIG. 3A) causes thecontactless card 101 and/or the server 120 to transfer the accountnumber, expiration date, the CVV, and the billing address to the accountapplication 113 (e.g., in an NDEF file). In some embodiments, theaccount application 113 may provide the account number from the NDEFfile to the autofill service 114 responsive to the first tap incombination with detection and identification of the data necessary fora field currently in focus (e.g., the account number field). Theautofill service 114 may then autofill the account number to an accountnumber form field. Responsive to the second tap, the account application113 may provide the expiration date from the NDEF file to the autofillservice 114 based on detecting and identifying the data necessary forthe field currently in focus (e.g., the expiration date field) andwithout having to receive any additional data from the contactless card101 and/or the server 120. The autofill service 114 may then autofillthe expiration date to one or more expiration date fields of the form.Responsive to the third tap, the account application 113 provides theCVV from the NDEF file to the to the autofill service 114 based ondetecting and identifying the data necessary for the field currently infocus (e.g., the CVV field) and without having to receive any additionaldata from the contactless card 101 and/or the server 120. The autofillservice 114 may then autofill the CVV to a CVV form field. If additionalfields are present (e.g., a name field, billing address field, etc.),additional taps of the contactless card 101 cause the accountapplication 113 to provide the corresponding data elements (e.g., theaccount holder name, billing address, etc.) to the autofill service 114based on detecting and identifying the data necessary for the fieldcurrently in focus and without having to receive any additional datafrom the contactless card 101 and/or the server 120. The autofillservice 114 may then autofill the data to the form fields (e.g., thebilling address to the billing address field, the name to the namefield, etc.).

FIG. 4A illustrates a contactless card 101, which may comprise a paymentcard, such as a credit card, debit card, and/or a gift card. As shown,the contactless card 101 may be issued by a service provider 405displayed on the front or back of the card 101. In some examples, thecontactless card 101 is not related to a payment card, and may comprise,without limitation, an identification card. In some examples, thepayment card may comprise a dual interface contactless payment card. Thecontactless card 101 may comprise a substrate 410, which may include asingle layer or one or more laminated layers composed of plastics,metals, and other materials. Exemplary substrate materials includepolyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadienestyrene, polycarbonate, polyesters, anodized titanium, palladium, gold,carbon, paper, and biodegradable materials. In some examples, thecontactless card 101 may have physical characteristics compliant withthe ID-1 format of the ISO/IEC 7810 standard, and the contactless cardmay otherwise be compliant with the ISO/IEC 14443 standard. However, itis understood that the contactless card 101 according to the presentdisclosure may have different characteristics, and the presentdisclosure does not require a contactless card to be implemented in apayment card.

The contactless card 101 may also include identification information 415displayed on the front and/or back of the card, and a contact pad 420.The contact pad 420 may be configured to establish contact with anothercommunication device, such as the mobile devices 110, a user device,smart phone, laptop, desktop, or tablet computer. The contactless card101 may also include processing circuitry, antenna and other componentsnot shown in FIG. 4A. These components may be located behind the contactpad 420 or elsewhere on the substrate 410. The contactless card 101 mayalso include a magnetic strip or tape, which may be located on the backof the card (not shown in FIG. 4A).

As illustrated in FIG. 4B, the contact pad 420 of contactless card 101may include processing circuitry 425 for storing and processinginformation, including a microprocessor 430 and the memory 102. It isunderstood that the processing circuitry 425 may contain additionalcomponents, including processors, memories, error and parity/CRCcheckers, data encoders, anticollision algorithms, controllers, commanddecoders, security primitives and tamperproofing hardware, as necessaryto perform the functions described herein.

The memory 102 may be a read-only memory, write-once read-multiplememory or read/write memory, e.g., RAM, ROM, and EEPROM, and thecontactless card 101 may include one or more of these memories. Aread-only memory may be factory programmable as read-only or one-timeprogrammable. One-time programmability provides the opportunity to writeonce then read many times. A write once/read-multiple memory may beprogrammed at a point in time after the memory chip has left thefactory. Once the memory is programmed, it may not be rewritten, but itmay be read many times. A read/write memory may be programmed andre-programed many times after leaving the factory. A read/write memorymay also be read many times after leaving the factory.

The memory 102 may be configured to store one or more applets 440, oneor more counters 104, a customer identifier 107, and the virtual accountnumbers 108. The one or more applets 440 may comprise one or moresoftware applications configured to execute on one or more contactlesscards, such as a Java® Card applet. However, it is understood thatapplets 440 are not limited to Java Card applets, and instead may be anysoftware application operable on contactless cards or other deviceshaving limited memory. The one or more counters 104 may comprise anumeric counter sufficient to store an integer. The customer identifier107 may comprise a unique alphanumeric identifier assigned to a user ofthe contactless card 101, and the identifier may distinguish the user ofthe contactless card from other contactless card users. In someexamples, the customer identifier 107 may identify both a customer andan account assigned to that customer and may further identify thecontactless card associated with the customer's account. As stated, theaccount numbers 108 may include thousands of one-time use virtualaccount numbers associated with the contactless card 101. An applet 440of the contactless card 101 may be configured to manage the accountnumbers 108 (e.g., to select an account number 108, mark the selectedaccount number 108 as used, and transmit the account number 108 to themobile device 110 for autofilling by the autofill service 114).

The processor and memory elements of the foregoing exemplary embodimentsare described with reference to the contact pad, but the presentdisclosure is not limited thereto. It is understood that these elementsmay be implemented outside of the pad 420 or entirely separate from it,or as further elements in addition to processor 430 and memory 102elements located within the contact pad 420.

In some examples, the contactless card 101 may comprise one or moreantennas 455. The one or more antennas 455 may be placed within thecontactless card 101 and around the processing circuitry 425 of thecontact pad 420. For example, the one or more antennas 455 may beintegral with the processing circuitry 425 and the one or more antennas455 may be used with an external booster coil. As another example, theone or more antennas 455 may be external to the contact pad 420 and theprocessing circuitry 425.

In an embodiment, the coil of contactless card 101 may act as thesecondary of an air core transformer. The terminal may communicate withthe contactless card 101 by cutting power or amplitude modulation. Thecontactless card 101 may infer the data transmitted from the terminalusing the gaps in the contactless card's power connection, which may befunctionally maintained through one or more capacitors. The contactlesscard 101 may communicate back by switching a load on the contactlesscard's coil or load modulation. Load modulation may be detected in theterminal's coil through interference. More generally, using the antennas455, processing circuitry 425, and/or the memory 102, the contactlesscard 101 provides a communications interface to communicate via NFC,Bluetooth, and/or Wi-Fi communications.

As explained above, contactless cards 101 may be built on a softwareplatform operable on smart cards or other devices having limited memory,such as JavaCard, and one or more or more applications or applets may besecurely executed. Applets 440 may be added to contactless cards toprovide a one-time password (OTP) for multifactor authentication (MFA)in various mobile application-based use cases. Applets 440 may beconfigured to respond to one or more requests, such as near field dataexchange requests, from a reader, such as a mobile NFC reader (e.g., ofthe mobile device 110), and produce an NDEF message that comprises acryptographically secure OTP encoded as an NDEF text tag.

One example of an NDEF OTP is an NDEF short-record layout (SR=1). Insuch an example, one or more applets 440 may be configured to encode theOTP as an NDEF type 4 well known type text tag. In some examples, NDEFmessages may comprise one or more records. The applets 440 may beconfigured to add one or more static tag records in addition to the OTPrecord.

In some examples, the one or more applets 440 may be configured toemulate an RFID tag. The RFID tag may include one or more polymorphictags. In some examples, each time the tag is read, differentcryptographic data is presented that may indicate the authenticity ofthe contactless card. Based on the one or more applications, an NFC readof the tag may be processed, the data may be transmitted to a server,such as the server 120, and the data may be validated at the server.

In some examples, the contactless card 101 and server 120 may includecertain data such that the card may be properly identified. Thecontactless card 101 may comprise one or more unique identifiers (notpictured). Each time a read operation takes place, the counters 104 maybe configured to increment. In some examples, each time data from thecontactless card 101 is read (e.g., by a mobile device 110), the counter104 is transmitted to the server for validation and determines whetherthe counter values 104 are equal (as part of the validation).

The one or more counters 104 may be configured to prevent a replayattack. For example, if a cryptogram has been obtained and replayed,that cryptogram is immediately rejected if the counter 104 has been reador used or otherwise passed over. If the counter 104 has not been used,it may be replayed. In some examples, the counter that is incremented onthe card is different from the counter that is incremented fortransactions. The contactless card 101 is unable to determine theapplication transaction counter 104 since there is no communicationbetween applets 440 on the contactless card 101. In some examples, thecontactless card 101 may comprise a first applet 440-1, which may be atransaction applet, and a second applet 440-2. Each applet 440-1 and440-2 may comprise a respective counter 104.

In some examples, the counter 104 may get out of sync. In some examples,to account for accidental reads that initiate transactions, such asreading at an angle, the counter 104 may increment but the applicationdoes not process the counter 104. In some examples, when the mobiledevice 110 is woken up, NFC may be enabled and the device 110 may beconfigured to read available tags, but no action is taken responsive tothe reads.

To keep the counter 104 in sync, an application, such as a backgroundapplication, may be executed that would be configured to detect when themobile device 110 wakes up and synchronize with the server 120indicating that a read that occurred due to detection to then move thecounter 104 forward. In other examples, Hashed One Time Password may beutilized such that a window of mis-synchronization may be accepted. Forexample, if within a threshold of 10, the counter 104 may be configuredto move forward. But if within a different threshold number, for examplewithin 10 or 1000, a request for performing re-synchronization may beprocessed which requests via one or more applications that the user tap,gesture, or otherwise indicate one or more times via the user's device.If the counter 104 increases in the appropriate sequence, then itpossible to know that the user has done so.

The key diversification technique described herein with reference to thecounter 104, master key 105, and diversified key 106 is one example ofencryption and/or decryption a key diversification technique. Thisexample key diversification technique should not be considered limitingof the disclosure, as the disclosure is equally applicable to othertypes of key diversification techniques.

During the creation process of the contactless card 101, twocryptographic keys may be assigned uniquely per card. The cryptographickeys may comprise symmetric keys which may be used in both encryptionand decryption of data. Triple DES (3DES) algorithm may be used by EMVand it is implemented by hardware in the contactless card 101. By usingthe key diversification process, one or more keys may be derived from amaster key based upon uniquely identifiable information for each entitythat requires a key.

In some examples, to overcome deficiencies of 3DES algorithms, which maybe susceptible to vulnerabilities, a session key may be derived (such asa unique key per session) but rather than using the master key, theunique card-derived keys and the counter may be used as diversificationdata. For example, each time the contactless card 101 is used inoperation, a different key may be used for creating the messageauthentication code (MAC) and for performing the encryption. Thisresults in a triple layer of cryptography. The session keys may begenerated by the one or more applets and derived by using theapplication transaction counter with one or more algorithms (as definedin EMV 4.3 Book 2 A1.3.1 Common Session Key Derivation).

Further, the increment for each card may be unique, and assigned eitherby personalization, or algorithmically assigned by some identifyinginformation. For example, odd numbered cards may increment by 2 and evennumbered cards may increment by 5. In some examples, the increment mayalso vary in sequential reads, such that one card may increment insequence by 1, 3, 5, 2, 2, . . . repeating. The specific sequence oralgorithmic sequence may be defined at personalization time, or from oneor more processes derived from unique identifiers. This can make itharder for a replay attacker to generalize from a small number of cardinstances.

The authentication message may be delivered as the content of a textNDEF record in hexadecimal ASCII format. In another example, the NDEFrecord may be encoded in hexadecimal format.

FIG. 5 illustrates an embodiment of a logic flow 500. The logic flow 500may be representative of some or all of the operations executed by oneor more embodiments described herein. For example, the logic flow 500may include some or all of the operations to securely autofill dataassociated with a contactless card 101 to a form using keydiversification. Embodiments are not limited in this context.

As shown, the logic flow 500 begins at block 505, where the accountapplication 113, the OS 112, and/or the autofill service 114 determinethat a payment field of a form has received focus. For example, a usermay tap the payment field of the form to give the payment field focus.As another example, the user may select the payment field of the formusing a mouse and/or keyboard. More generally, any technique may be usedto give the payment field focus, including programmatically generatedfocus. For example, the payment field may receive focus based on thehypertext markup language (HTML) “focus( )” method. As another example,the payment field may automatically receive focus when the form isloaded, e.g., based on the “autofocus” HTML attribute being applied tothe payment field in source code. The payment field may include one ormore of a name field, an account number field, expiration date field, ashipping address field, a billing address field, and/or a CVV field.Once the payment field receives focus, the account application 113, theOS 112, and/or the autofill service 114 may output a notificationspecifying to the user to tap the contactless card 101 to the mobiledevice 110. In some embodiments, the notification may be generated basedon a determination that the form includes one or more payment fields.The notification may include a GUI which shows depicts an example of howto tap the contactless card 101 to the mobile device 110. At block 510,a user taps the contactless card 101 to the mobile device to cause thecontactless card 101 to generate and transmit encrypted data (e.g., theencrypted customer ID 109). The user may tap the contactless card 101responsive to a notification specifying to tap the contactless card 101to autofill account-related data into the form. The account application113 may transmit an indication to the contactless card 101 via the NFCcard reader 118 specifying to generate and transmit encrypted data. Thecontactless card 101 may increment the counter value 104 in the memory102 responsive to receiving the indication to generate encrypted data.At block 515, the contactless card 101 generates the diversified key 106using the counter value 104 and the master key 105 in the memory 102 anda cryptographic algorithm. At block 520, the contactless card 101encrypts data (e.g., the customer identifier 107) using the diversifiedkey 106 and the cryptographic algorithm, generating encrypted data(e.g., the encrypted customer ID 109).

At block 525, the contactless card 101 may transmit the encrypted datato the account application 113 of the mobile device 110, e.g., usingNFC. In at least one embodiment, the contactless card 101 furtherincludes an indication of the counter value 104 along with the encrypteddata. At block 530, the account application 113 of the mobile device 110may transmit the data received from the contactless card 101 to themanagement application 123 of the server 120. At block 535, themanagement application 123 of the server 120 may generate a diversifiedkey 106 using the master key 105 and the counter value 104 as input to acryptographic algorithm. In one embodiment, the management application123 uses the counter value 104 provided by the contactless card 101. Inanother embodiment, the management application 123 increments thecounter value 104 in the memory 122 to synchronize the state of thecounter value 104 in the memory 122 with the counter value 104 in thememory 102 of the contactless card 101.

At block 540, the management application 123 decrypts the encrypted datareceived from the contactless card 101 via the mobile device 110 usingthe diversified key 106 and a cryptographic algorithm. Doing so mayyield at least the customer identifier 107. By yielding the customeridentifier 107, the management application 123 may validate the datareceived from the contactless card 101 at block 545. For example, themanagement application 123 may compare the customer identifier 107 to acustomer identifier for the associated account in the account data 124,and validate the data based on a match.

At block 550, the management application 123 may transmit card data 103associated with the contactless card 101 to the account application 113of the mobile device 110. For example, the management application 123may transmit the account number, expiration date, shipping address,billing address, and CVV. The management application 123 may furthertransmit the name of the account holder. In one embodiment, themanagement application 123 generates a virtual account number that issent to the account application 113 of the mobile device 110. At block555, the account application 113 of the mobile device 110 provides thecard data 103 received from the server 120 to an API of the autofillservice 114 of the OS 112. At block 560, the autofill service 114automatically fills the card data 103 (or at least a portion thereof) toone or more fields of a form. For example, if the form field thatreceived focus is an account number field, the autofill service 114 mayautofill the account number to the account number field. In someembodiments, the autofill service 114 fills all payment fields of theform (e.g., the account number, expiration date, CVV value, billingaddress, and account holder name) at block 560. The form may be acomponent of the account application 113, the other applications 115,and/or the OS 112.

FIG. 6 illustrates an embodiment of a logic flow 600. The logic flow 600may be representative of some or all of the operations executed by oneor more embodiments described herein. For example, the logic flow 600may include some or all of the operations to autofill virtual cardnumbers stored in the contactless card 101. Embodiments are not limitedin this context.

As shown, the logic flow 600 begins at block 610, where a user taps thecontactless card 101 to the mobile device 110. For example, the accountapplication 113 and/or the autofill service 114 may determine that apayment field of a form has received focus and output a notification totap the contactless card 101 to the mobile device 110. Doing so causesthe account application 113 to transmit an indication to the contactlesscard 101 via the card reader 118 to transmit one of the account numbers108 to the mobile device 110. At block 620, an applet 440 of thecontactless card 101 selects a record from the account numbers 108. Theapplet 440 may encrypt the virtual account number, CVV, and expirationdate of the selected record. The applet 440 may further generate anencrypted customer ID 109 using the key diversification techniquedescribed above. The applet 440 may then transmit the encrypted recordfrom the account numbers 108 (which may include the encrypted virtualaccount number, expiration date, and CVV) and the encrypted customer ID109 to the account application 113 of the mobile device 110 via NFC. Theaccount application 113 may forward the encrypted customer ID 109 to theserver 120 for verification as described above. At block 630, the applet440 of the contactless card 101 modifies the virtual account numbers 108to reflect the read of the virtual account number at block 620. Forexample, the applet 440 may delete the record for the virtual accountnumber read at block 620 from the account numbers 108.

At block 635, the account application 113 transmits the encryptedcustomer ID 109 to the management application 123 of the server 120. Atblock 640, the account application 113 receives an indication from theserver 120 that the management application 123 verified the encryptedcustomer ID 109 as described above. Doing so enhances security of thevirtual account number 108. At block 650, the account application 113decrypts the encrypted data received from the contactless card 101,yielding the virtual account number, expiration date, CVV, and username. At block 660, the account application 113 may provide thedecrypted data to the autofill service 114. The account application 113may further provide additional information such as the billing addressand the account holder name to the autofill service 114. At block 670,the autofill service 114 autofills the data (including virtual accountnumber, expiration date, and CVV) to a form of the account application113, other applications 115, and/or the OS 112.

FIG. 7 illustrates an embodiment of a logic flow 700. The logic flow 700may be representative of some or all of the operations executed by oneor more embodiments described herein. For example, the logic flow 700may include some or all of the operations to autofill card data 103stored in the contactless card 101. Embodiments are not limited in thiscontext.

As shown, the logic flow 700 begins at block 710, where a user taps thecontactless card 101 to the mobile device 110. For example, the accountapplication 113 and/or the autofill service 114 may determine that apayment field of a form has received focus and output a notification totap the contactless card 101 to the mobile device 110. As anotherexample, the account application 113 and/or the autofill service 114 maydetermine that the form includes payment fields (e.g., based on themetadata of each form field). Doing so causes the account application113 to transmit an indication to the contactless card 101 via the cardreader 118 to transmit the card data 103 via the EMV protocol. At block720, the contactless card 101 transmits the card data 103 to the accountapplication 113 via the EMV protocol. The card data 103 may include theaccount number (e.g., PAN), expiration date, and account holder's name.In some embodiments, the card data 103 may further include the CVV.

At block 730, the account application 113 receives the card data 103from the contactless card 101. At block 740, the account application 113provides the received card data 103 to the API of the autofill service114. At block 750, the autofill service 114 autofills the card data 103to a form, e.g., by populating at least the PAN to an account numberfield, the expiration date to an expiration date field. The autofillservice 114 may further autofill the account holder's name and CVV tothe corresponding form fields.

In some examples, the contactless card 101 may be tapped to a device,such as one or more computer kiosks or terminals, to verify identity soas to receive a transactional item responsive to a purchase, such as acoffee. By using the contactless card 101, a secure method of provingidentity in a loyalty program may be established. Securely proving theidentity, for example, to obtain a reward, coupon, offer, or the like orreceipt of a benefit is established in a manner that is different thanmerely scanning a bar card. For example, an encrypted transaction mayoccur between the contactless card 101 and the device, which mayconfigured to process one or more tap gestures. As explained above, theone or more applications may be configured to validate identity of theuser and then cause the user to act or respond to it, for example, viaone or more tap gestures. In some examples, data for example, bonuspoints, loyalty points, reward points, healthcare information, etc., maybe written back to the contactless card.

In some examples, the contactless card 101 may be tapped to a device,such as the mobile device 110. As explained above, identity of the usermay be verified by the one or more applications which would then grantthe user a desired benefit based on verification of the identity.

In some embodiments, an example authentication communication protocolmay mimic an offline dynamic data authentication protocol of the EMVstandard that is commonly performed between a transaction card and apoint-of-sale device, with some modifications. For example, because theexample authentication protocol is not used to complete a paymenttransaction with a card issuer/payment processor per se, some datavalues are not needed, and authentication may be performed withoutinvolving real-time online connectivity to the card issuer/paymentprocessor. As is known in the art, point of sale (POS) systems submittransactions including a transaction value to a card issuer. Whether theissuer approves or denies the transaction may be based on if the cardissuer recognizes the transaction value. Meanwhile, in certainembodiments of the present disclosure, transactions originating from amobile device lack the transaction value associated with the POSsystems. Therefore, in some embodiments, a dummy transaction value(i.e., a value recognizable to the card issuer and sufficient to allowactivation to occur) may be passed as part of the example authenticationcommunication protocol. POS based transactions may also declinetransactions based on the number of transaction attempts (e.g.,transaction counter). A number of attempts beyond a buffer value mayresult in a soft decline; the soft decline requiring furtherverification before accepting the transaction. In some implementations,a buffer value for the transaction counter may be modified to avoiddeclining legitimate transactions.

In some examples, the contactless card 101 can selectively communicateinformation depending upon the recipient device. Once tapped, thecontactless card 101 can recognize the device to which the tap isdirected, and based on this recognition the contactless card can provideappropriate data for that device. This advantageously allows thecontactless card to transmit only the information required to completethe instant action or transaction, such as a payment or cardauthentication. By limiting the transmission of data and avoiding thetransmission of unnecessary data, both efficiency and data security canbe improved. The recognition and selective communication of informationcan be applied to a various scenarios, including card activation,balance transfers, account access attempts, commercial transactions, andstep-up fraud reduction.

If the tap of the contactless card 101 is directed to a device runningApple's iOS® operating system, e.g., an iPhone, iPod, or iPad, thecontactless card can recognize the iOS® operating system and transmitdata appropriate data to communicate with this device. For example, thecontactless card 101 can provide the encrypted identity informationnecessary to authenticate the card using NDEF tags via, e.g., NFC.Similarly, if the contactless card tap is directed to a device runningthe Android® operating system, e.g., an Android® smartphone or tablet,the contactless card can recognize the Android® operating system andtransmit appropriate and data to communicate with this device (such asthe encrypted identity information necessary for authentication by themethods described herein).

As another example, the contactless card tap can be directed to a POSdevice, including without limitation a kiosk, a checkout register, apayment station, or other terminal. Upon performance of the tap, thecontactless card 101 can recognize the POS device and transmit only theinformation necessary for the action or transaction. For example, uponrecognition of a POS device used to complete a commercial transaction,the contactless card 101 can communicate payment information necessaryto complete the transaction under the EMV standard.

In some examples, the POS devices participating in the transaction canrequire or specify additional information, e.g., device-specificinformation, location-specific information, and transaction-specificinformation, that is to be provided by the contactless card. Forexample, once the POS device receives a data communication from thecontactless card, the POS device can recognize the contactless card andrequest the additional information necessary to complete an action ortransaction.

In some examples the POS device can be affiliated with an authorizedmerchant or other entity familiar with certain contactless cards oraccustomed to performing certain contactless card transactions. However,it is understood such an affiliation is not required for the performanceof the described methods.

In some examples, such as a shopping store, grocery store, conveniencestore, or the like, the contactless card 101 may be tapped to a mobiledevice without having to open an application, to indicate a desire orintent to utilize one or more of reward points, loyalty points, coupons,offers, or the like to cover one or more purchases. Thus, an intentionbehind the purchase is provided.

In some examples, the one or more applications may be configured todetermine that it was launched via one or more tap gestures of thecontactless card 101, such that a launch occurred at 3:51 pm, that atransaction was processed or took place at 3:56 pm, in order to verifyidentity of the user.

In some examples, the one or more applications may be configured tocontrol one or more actions responsive to the one or more tap gestures.For example, the one or more actions may comprise collecting rewards,collecting points, determine the most important purchase, determine theleast costly purchase, and/or reconfigure, in real-time, to anotheraction.

In some examples, data may be collected on tap behaviors asbiometric/gestural authentication. For example, a unique identifier thatis cryptographically secure and not susceptible to interception may betransmitted to one or more backend services. The unique identifier maybe configured to look up secondary information about individual. Thesecondary information may comprise personally identifiable informationabout the user. In some examples, the secondary information may bestored within the contactless card.

In some examples, the device may comprise an application that splitsbills or check for payment amongst a plurality of individuals. Forexample, each individual may possess a contactless card, and may becustomers of the same issuing financial institution, but it is notnecessary. Each of these individuals may receive a push notification ontheir device, via the application, to split the purchase. Rather thanaccepting only one card tap to indicate payment, other contactless cardsmay be used. In some examples, individuals who have different financialinstitutions may possess contactless cards 101 to provide information toinitiate one or more payment requests from the card-tapping individual.

In some examples, the present disclosure refers to a tap of thecontactless card. However, it is understood that the present disclosureis not limited to a tap, and that the present disclosure includes othergestures (e.g., a wave or other movement of the card).

FIG. 8 illustrates an embodiment of an exemplary computing architecture800 comprising a computing system 802 that may be suitable forimplementing various embodiments as previously described. In variousembodiments, the computing architecture 800 may comprise or beimplemented as part of an electronic device. In some embodiments, thecomputing architecture 800 may be representative, for example, of asystem that implements one or more components of the system 100. In someembodiments, computing system 802 may be representative, for example, ofthe mobile devices 110 and server 120 of the system 100. The embodimentsare not limited in this context. More generally, the computingarchitecture 800 is configured to implement all logic, applications,systems, methods, apparatuses, and functionality described herein withreference to FIGS. 1-6.

As used in this application, the terms “system” and “component” and“module” are intended to refer to a computer-related entity, eitherhardware, a combination of hardware and software, software, or softwarein execution, examples of which are provided by the exemplary computingarchitecture 800. For example, a component can be, but is not limited tobeing, a process running on a computer processor, a computer processor,a hard disk drive, multiple storage drives (of optical and/or magneticstorage medium), an object, an executable, a thread of execution, aprogram, and/or a computer. By way of illustration, both an applicationrunning on a server and the server can be a component. One or morecomponents can reside within a process and/or thread of execution, and acomponent can be localized on one computer and/or distributed betweentwo or more computers. Further, components may be communicativelycoupled to each other by various types of communications media tocoordinate operations. The coordination may involve the uni-directionalor bi-directional exchange of information. For instance, the componentsmay communicate information in the form of signals communicated over thecommunications media. The information can be implemented as signalsallocated to various signal lines. In such allocations, each message isa signal. Further embodiments, however, may alternatively employ datamessages. Such data messages may be sent across various connections.Exemplary connections include parallel interfaces, serial interfaces,and bus interfaces.

The computing system 802 includes various common computing elements,such as one or more processors, multi-core processors, co-processors,memory units, chipsets, controllers, peripherals, interfaces,oscillators, timing devices, video cards, audio cards, multimediainput/output (I/O) components, power supplies, and so forth. Theembodiments, however, are not limited to implementation by the computingsystem 802.

As shown in FIG. 8, the computing system 802 comprises a processor 804,a system memory 806 and a system bus 808. The processor 804 can be anyof various commercially available computer processors, including withoutlimitation an AMD® Athlon®, Duron® and Opteron® processors; ARM®application, embedded and secure processors; IBM® and Motorola®DragonBall® and PowerPC® processors; IBM and Sony® Cell processors;Intel® Celeron®, Core®, Core (2) Duo®, Itanium®, Pentium®, Xeon®, andXScale® processors; and similar processors. Dual microprocessors,multi-core processors, and other multi processor architectures may alsobe employed as the processor 804.

The system bus 808 provides an interface for system componentsincluding, but not limited to, the system memory 806 to the processor804. The system bus 808 can be any of several types of bus structurethat may further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. Interface adapters may connectto the system bus 808 via a slot architecture. Example slotarchitectures may include without limitation Accelerated Graphics Port(AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA),Micro Channel Architecture (MCA), NuBus, Peripheral ComponentInterconnect (Extended) (PCI(X)), PCI Express, Personal Computer MemoryCard International Association (PCMCIA), and the like.

The system memory 806 may include various types of computer-readablestorage media in the form of one or more higher speed memory units, suchas read-only memory (ROM), random-access memory (RAM), dynamic RAM(DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), staticRAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory (e.g., oneor more flash arrays), polymer memory such as ferroelectric polymermemory, ovonic memory, phase change or ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, magnetic or opticalcards, an array of devices such as Redundant Array of Independent Disks(RAID) drives, solid state memory devices (e.g., USB memory, solid statedrives (SSD) and any other type of storage media suitable for storinginformation. In the illustrated embodiment shown in FIG. 8, the systemmemory 806 can include non-volatile memory 810 and/or volatile memory812. A basic input/output system (BIOS) can be stored in thenon-volatile memory 810.

The computing system 802 may include various types of computer-readablestorage media in the form of one or more lower speed memory units,including an internal (or external) hard disk drive (HDD) 814, amagnetic floppy disk drive (FDD) 816 to read from or write to aremovable magnetic disk 818, and an optical disk drive 820 to read fromor write to a removable optical disk 822 (e.g., a CD-ROM or DVD). TheHDD 814, FDD 816 and optical disk drive 820 can be connected to thesystem bus 808 by a HDD interface 824, an FDD interface 826 and anoptical drive interface 828, respectively. The HDD interface 824 forexternal drive implementations can include at least one or both ofUniversal Serial Bus (USB) and IEEE 1394 interface technologies. Thecomputing system 802 is generally is configured to implement all logic,systems, methods, apparatuses, and functionality described herein withreference to FIGS. 1-7.

The drives and associated computer-readable media provide volatileand/or nonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For example, a number of program modules canbe stored in the drives and memory units 810, 812, including anoperating system 830, one or more application programs 832, otherprogram modules 834, and program data 836. In one embodiment, the one ormore application programs 832, other program modules 834, and programdata 836 can include, for example, the various applications and/orcomponents of the system 100, e.g., the operating system 112, accountapplication 113, autofill service 114, other applications 115, clipboard116, accessibility service 117, and the management application 123.

A user can enter commands and information into the computing system 802through one or more wire/wireless input devices, for example, a keyboard838 and a pointing device, such as a mouse 840. Other input devices mayinclude microphones, infra-red (IR) remote controls, radio-frequency(RF) remote controls, game pads, stylus pens, card readers, dongles,finger print readers, gloves, graphics tablets, joysticks, keyboards,retina readers, touch screens (e.g., capacitive, resistive, etc.),trackballs, trackpads, sensors, styluses, and the like. These and otherinput devices are often connected to the processor 804 through an inputdevice interface 842 that is coupled to the system bus 808, but can beconnected by other interfaces such as a parallel port, IEEE 1394 serialport, a game port, a USB port, an IR interface, and so forth.

A monitor 844 or other type of display device is also connected to thesystem bus 808 via an interface, such as a video adaptor 846. Themonitor 844 may be internal or external to the computing system 802. Inaddition to the monitor 844, a computer typically includes otherperipheral output devices, such as speakers, printers, and so forth.

The computing system 802 may operate in a networked environment usinglogical connections via wire and/or wireless communications to one ormore remote computers, such as a remote computer 848. The remotecomputer 848 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computingsystem 802, although, for purposes of brevity, only a memory/storagedevice 850 is illustrated. The logical connections depicted includewire/wireless connectivity to a local area network (LAN) 852 and/orlarger networks, for example, a wide area network (WAN) 854. Such LANand WAN networking environments are commonplace in offices andcompanies, and facilitate enterprise-wide computer networks, such asintranets, all of which may connect to a global communications network,for example, the Internet. In embodiments, the network 130 of FIG. 1 isone or more of the LAN 852 and the WAN 854.

When used in a LAN networking environment, the computing system 802 isconnected to the LAN 852 through a wire and/or wireless communicationnetwork interface or adaptor 856. The adaptor 856 can facilitate wireand/or wireless communications to the LAN 852, which may also include awireless access point disposed thereon for communicating with thewireless functionality of the adaptor 856.

When used in a WAN networking environment, the computing system 802 caninclude a modem 858, or is connected to a communications server on theWAN 854, or has other means for establishing communications over the WAN854, such as by way of the Internet. The modem 858, which can beinternal or external and a wire and/or wireless device, connects to thesystem bus 808 via the input device interface 842. In a networkedenvironment, program modules depicted relative to the computing system802, or portions thereof, can be stored in the remote memory/storagedevice 850. It will be appreciated that the network connections shownare exemplary and other means of establishing a communications linkbetween the computers can be used.

The computing system 802 is operable to communicate with wired andwireless devices or entities using the IEEE 802 family of standards,such as wireless devices operatively disposed in wireless communication(e.g., IEEE 802.16 over-the-air modulation techniques). This includes atleast Wi-Fi (or Wireless Fidelity), WiMax, and Bluetooth™ wirelesstechnologies, among others. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices. Wi-Fi networks use radiotechnologies called IEEE 802.11x (a, b, g, n, etc.) to provide secure,reliable, fast wireless connectivity. A Wi-Fi network can be used toconnect computers to each other, to the Internet, and to wire networks(which use IEEE 802.3-related media and functions).

Various embodiments may be implemented using hardware elements, softwareelements, or a combination of both. Examples of hardware elements mayinclude processors, microprocessors, circuits, circuit elements (e.g.,transistors, resistors, capacitors, inductors, and so forth), integratedcircuits, application specific integrated circuits (ASIC), programmablelogic devices (PLD), digital signal processors (DSP), field programmablegate array (FPGA), logic gates, registers, semiconductor device, chips,microchips, chip sets, and so forth. Examples of software may includesoftware components, programs, applications, computer programs,application programs, system programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an embodimentis implemented using hardware elements and/or software elements may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints.

One or more aspects of at least one embodiment may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that make the logic or processor. Some embodiments may beimplemented, for example, using a machine-readable medium or articlewhich may store an instruction or a set of instructions that, ifexecuted by a machine, may cause the machine to perform a method and/oroperations in accordance with the embodiments. Such a machine mayinclude, for example, any suitable processing platform, computingplatform, computing device, processing device, computing system,processing system, computer, processor, or the like, and may beimplemented using any suitable combination of hardware and/or software.The machine-readable medium or article may include, for example, anysuitable type of memory unit, memory device, memory article, memorymedium, storage device, storage article, storage medium and/or storageunit, for example, memory, removable or non-removable media, erasable ornon-erasable media, writeable or re-writeable media, digital or analogmedia, hard disk, floppy disk, Compact Disk Read Only Memory (CD-ROM),Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW),optical disk, magnetic media, magneto-optical media, removable memorycards or disks, various types of Digital Versatile Disk (DVD), a tape, acassette, or the like. The instructions may include any suitable type ofcode, such as source code, compiled code, interpreted code, executablecode, static code, dynamic code, encrypted code, and the like,implemented using any suitable high-level, low-level, object-oriented,visual, compiled and/or interpreted programming language.

The foregoing description of example embodiments has been presented forthe purposes of illustration and description. It is not intended to beexhaustive or to limit the present disclosure to the precise formsdisclosed. Many modifications and variations are possible in light ofthis disclosure. It is intended that the scope of the present disclosurebe limited not by this detailed description, but rather by the claimsappended hereto. Future filed applications claiming priority to thisapplication may claim the disclosed subject matter in a differentmanner, and may generally include any set of one or more limitations asvariously disclosed or otherwise demonstrated herein.

1-20. (canceled)
 21. A computer-implemented method, comprising: receiving, by an application executing on a processor, encrypted data from a contactless card; transmitting, by the application, the encrypted data to a server; receiving, by the application from the server, an account number; providing, by the application, the account number to an autofill service of an operating system (OS) executing on the processor; and autofilling, by the autofill service, the account number to a payment field of a form.
 22. The computer-implemented method of claim 21, further comprising prior to providing the account number to the autofill service: determining, by the application based on a decryption result received from the server, that the server decrypted the encrypted data.
 23. The computer-implemented method of claim 21, wherein the account number received from the server is encrypted, the method further comprising: decrypting the encrypted account number by the application prior to providing the account number to the autofill service.
 24. The computer-implemented method of claim 21, further comprising prior to receiving the encrypted data: determining, by the application, that the payment field of the form has received focus.
 25. The computer-implemented method of claim 21, wherein the account number is provided to an application programming interface (API) of the autofill service.
 26. The computer-implemented method of claim 21, further comprising: receiving, by the application from the server, an expiration date of the account number and a card verification value (CVV) of the account number; providing, by the application to the autofill service, the expiration date and the CVV; and autofilling, by the autofill service: (i) the expiration date to an expiration date field of the form, and (ii) the CVV to a CVV field of the form.
 27. The computer-implemented method of claim 21, wherein the account number comprises: (i) an account number of the contactless card, (ii) a virtual account number, or (iii) a token.
 28. A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a processor, cause the processor to: receive, by an application, encrypted data from a contactless card; transmit, by the application, the encrypted data to a server; receive, by the application from the server, an account number; provide, by the application, the account number to an autofill service of an operating system (OS); and autofill, by the autofill service, the account number to a payment field of a form.
 29. The computer-readable storage medium of claim 28, wherein the instructions further cause the processor to, prior to providing the account number to the autofill service: determine, by the application based on a decryption result received from the server, that the server decrypted the encrypted data.
 30. The computer-readable storage medium of claim 28, wherein the account number received from the server is encrypted, wherein the instructions further cause the processor to: decrypt the encrypted account number by the application prior to providing the account number to the autofill service.
 31. The computer-readable storage medium of claim 28, wherein the instructions further cause the processor to, prior to receiving the encrypted data: determine, by the application, that the payment field of the form has received focus.
 32. The computer-readable storage medium of claim 28, wherein the account number is provided to an application program interface (API) of the autofill service.
 33. The computer-readable storage medium of claim 28, wherein the instructions further cause the processor to: receive, by the application from the server, an expiration date of the account number and a card verification value (CVV) of the account number; provide, by the application to the autofill service, the expiration date and the CVV; and autofill, by the autofill service: (i) the expiration date to an expiration date field of the form, and (ii) the CVV to a CVV field of the form.
 34. The computer-readable storage medium of claim 28, wherein the account number comprises: (i) an account number of the contactless card, (ii) a virtual account number, or (iii) a token.
 35. A computing apparatus comprising: a processor; and a memory storing instructions that, when executed by the processor, cause the processor to: receive, by an application, encrypted data from a contactless card; transmit, by the application, the encrypted data to a server; receive, by the application from the server, an account number; provide, by the application, the account number to an autofill service of an operating system (OS); and autofill, by the autofill service, the account number to a payment field of a form.
 36. The computing apparatus of claim 35, wherein the instructions further cause the processor to, prior to providing the account number to the autofill service: determine, by the application based on a decryption result received from the server, that the server decrypted the encrypted data.
 37. The computing apparatus of claim 35, wherein the account number received from the server is encrypted, wherein the instructions further cause the processor to: decrypt the encrypted account number by the application prior to providing the account number to the autofill service.
 38. The computing apparatus of claim 35, wherein the instructions further cause the processor to, prior to receiving the encrypted data: determine, by the application, that the payment field of the form has received focus.
 39. The computing apparatus of claim 35, wherein the account number is provided to an application program interface (API) of the autofill service.
 40. The computing apparatus of claim 35, wherein the instructions further cause the processor to: receive, by the application from the server, an expiration date of the account number and a card verification value (CVV) of the account number; provide, by the application to the autofill service, the expiration date and the CVV; and autofill, by the autofill service: (i) the expiration date to an expiration date field of the form, and (ii) the CVV to a CVV field of the form. 